Cryptext x64 0.11v fix2 - Legacy SHA-1 byte-order compatibility
================================================================

Problem found with real Cryptext 3.4 files:
Windows CNG BCryptFinishHash returns the normal SHA-1 digest byte order.
The original Cryptext SHA implementation exposed its five 32-bit digest words
in native little-endian memory order.  Therefore every 4-byte SHA-1 word must
be byte-swapped when reproducing the old format.

Confirmed from two genuine 32-byte (zero-length plaintext) Cryptext 3.4 files:

Password: Test123
Stored trailer check:
41ecfd41cc3e100559eb7f1635114190ea3a63e4
Calculated after legacy word conversion:
41ecfd41cc3e100559eb7f1635114190ea3a63e4

Password: N0tS3cure123!
Stored trailer check:
e7daed256c50fb79e49f1ed857df53d7a4b62d3f
Calculated after legacy word conversion:
e7daed256c50fb79e49f1ed857df53d7a4b62d3f

The conversion is applied in Legacy34_SHA1 so passwordHash, password check,
and the per-file RC4 key all use the original Cryptext byte representation.
Modern CT64FILE v1 code is untouched.
